Code review for and by scientists: preliminary findings

We describe two pilot studies of code review by and for scientists. Our principal findings are that scien- tists are enthusiastic, but need to be shown code re- view in action, and that just-in-time review of small code changes is more likely to succeed than large-scale end-of-work reviews

Project-based Learning Practices in Computer Science Education

The EPCoS project (Effective Projectwork in Computer Science) is working to map the range of project-based learning practices in UK higher education and to generate insights into what characterizes the contexts in which particular techniques are effective. In assembling a body of authentic examples, EPCoS aims to provide a resource that enables extrapolation and synthesis of new techniques. To allow educators and researchers to mine this material, EPCoS is systematizing it within a template-based catalogue, augmented with indexing and abstracting devices. Moreover, EPCoS is examining the process by which practices are transferred between institutional contexts, with a view to identifying effective models of the transfer process. Three key elements of transfer are the identification of appropriate practices, the selection of a practice for a purpose, and the integration of a chosen practice into the existing culture. Structured resources and process models are essential tools for supporting responsiveness in the current climate of continual change: the rapid development of computer technology is demanding new range and flexibility in project work, and EPCoS's mapping of project-based teaching allows practitioners to respond to these changes. This is one context in which educational research into how projects work can generalize to professional practice

Code Review For and By Scientists

We describe two pilot studies of code review by and for scientists. Our principal findings are that scientists are enthusiastic, but need to be shown code review in action, and that just-in-time review of small code changes is more likely to succeed than large-scale end-of-work reviews.Comment: 4 page

Computing word-of-mouth trust relationships in social networks from Semantic Web and Web 2.0 data sources

Social networks can serve as both a rich source of new information and as a filter to identify the information most relevant to our specific needs. In this paper we present a methodology and algorithms that, by exploiting existing Semantic Web and Web2.0 data sources, help individuals identify who in their social network knows what, and who is the most trustworthy source of information on that topic. Our approach improves upon previous work in a number of ways, such as incorporating topic-specific rather than global trust metrics. This is achieved by generating topic experience profiles for each network member, based on data from Revyu and del.icio.us, to indicate who knows what. Identification of the most trustworthy sources is enabled by a rich trust model of information and recommendation seeking in social networks. Reviews and ratings created on Revyu provide source data for algorithms that generate topic expertise and person to person affinity metrics. Combining these metrics, we are implementing a user-oriented application for searching and automated ranking of information sources within social networks

The mystery of the writing that isn’t on the wall: differences in public representations in traditional and agile software development

This paper considers the use of public displays, such as whiteboards and papers pinned to walls, by different software development teams, based on evidence from a number of empirical studies. This paper outlines differences in use observed between traditional and agile teams and begins to identify the implications that they may have for software development

Insights from expert software design practice

Software is a designed artifact. In other design disciplines, such as architecture, there is a well-established tradition of design studies which inform not only the discipline itself but also tool design, processes, and collaborative work. The 'challenge' of this paper is to consider software from such a 'design studies' perspective. This paper will present a series of observations from empirical studies of expert software designers, and will draw on examples from actual professional practice. It will consider what experts' mental imagery, software visualisations, and sketches suggest about software design thinking. It will also discuss some of the deliberate practices experts use to promote innovation. Finally, it will open discussion on the tensions between observed software design practices and received methodology in software engineering

UML in practice

UML has been described by some as “the lingua franca of software engineering”. Evidence from industry does not necessarily support such endorsements. How exactly is UML being used in industry – if it is? This paper presents a corpus of interviews with 50 professional software engineers in 50 companies and identifies 5 patterns of UML use

Miki: a wiki for synchronous modeling of software requirements

Eliciting a high quality requirements model that can be traced down to implementations is a challenge. Keeping models updated for evolving software systems is a further challenge. Formal modelling methods are one approach - but one that is too rigid and costly for many small software engineering companies [1]. We propose a light-weight alternative, using a wiki as the synchronous bridge between requirements capture and more formal modeling features of the IDE such as Eclipse